Dealing with Deadlines
Original Post
Hi Mark
I suspect I already know your answer to this but in the hope that you might have a solution....... :-)
I have clearly recognised that one of the reasons AF works so well for me is because I can do what I like when I like. I had assumed, reasonably enough I think, that my not wanting to be told when to do something (even by myself) would not impact on things I enjoyed doing. Someone else posted that they never had any problems with things they enjoyed doing and I thought I related to that, that my reasons for not doing things I enjoyed were purely down to my time management and the "guilt factor". However, I am finding a resistance to things I enjoy doing that have a deadline, so think that there is more of a deadline issue than I initially realised.
To be specific I have a talk to prepare for tomorow - that is something I will enjoy doing so the task itself is not the issue. I am not on the right page so that is a factor, but I could use the common sense rule (and obviously will do so if it gets to that stage). I have started the task so it is moving. I can see how the system will eventually get me to stage you are now at, of working primarily towards the end of your lists but I am not there yet. I know that I may have to action tasks "outside the system" (common sense/scheduled) but would prefer that to be the exception rather than the rule for all but static appointments.
I am just going to "trust the system" and strongly believe this issue will resolve itself once I get more proficient but have you found any solution to this problem yourself other than the common sense rule?
Actually I'm not really sure why I'm bothering to post this question Mark, other than that it has already helped me to get the issue clear in my head? I have a strong premonition that your answer will be "just trust the system and use the common sense rule where necessary!"
Thanks :-)
I suspect I already know your answer to this but in the hope that you might have a solution....... :-)
I have clearly recognised that one of the reasons AF works so well for me is because I can do what I like when I like. I had assumed, reasonably enough I think, that my not wanting to be told when to do something (even by myself) would not impact on things I enjoyed doing. Someone else posted that they never had any problems with things they enjoyed doing and I thought I related to that, that my reasons for not doing things I enjoyed were purely down to my time management and the "guilt factor". However, I am finding a resistance to things I enjoy doing that have a deadline, so think that there is more of a deadline issue than I initially realised.
To be specific I have a talk to prepare for tomorow - that is something I will enjoy doing so the task itself is not the issue. I am not on the right page so that is a factor, but I could use the common sense rule (and obviously will do so if it gets to that stage). I have started the task so it is moving. I can see how the system will eventually get me to stage you are now at, of working primarily towards the end of your lists but I am not there yet. I know that I may have to action tasks "outside the system" (common sense/scheduled) but would prefer that to be the exception rather than the rule for all but static appointments.
I am just going to "trust the system" and strongly believe this issue will resolve itself once I get more proficient but have you found any solution to this problem yourself other than the common sense rule?
Actually I'm not really sure why I'm bothering to post this question Mark, other than that it has already helped me to get the issue clear in my head? I have a strong premonition that your answer will be "just trust the system and use the common sense rule where necessary!"
Thanks :-)
Reply by Seraphim
Christine, what was the outcome? Can't wait to hear. :-)
Reply by Christine B
Actually the outcome was very interesting. I had pretty much free reign on the topic but had a fairly good idea as to what I was going to talk on. However preparing the talk didn't stand out and "just doing it" didn't feel the right approach. I had already done the basics on a Powerpoint presentation so had no problem finishing that off - the Powerpoint was incidental to the talk and did not specifically relate to the content. The amazing thing was that, when finalising the Powerpoint, my thoughts went off in a completely different direction and I prepared a totally different talk to what I had originally intended ............ So, yet again "trusting the system" came through for me .... :-)
Reply by Seraphim
The same thing happened for me on Wednesday. For two weeks I had needed to prepare a demo of our new system for some engineers, but I just kept resisting it. Finally on Weds morning the time was right, and I just cranked it out, and it all came together really well.
Part of me still questions and doubts... isn't this the same old college behavior, cramming before the test, waiting till the deadline before a superhuman effort is required to get the thing done, so I can get the adrenalin rush of an amazing achievement?
But then part of me answers back -- maybe there's some value to this kind of procrastination -- letting things stew till their properly cooked. :-)
Part of me still questions and doubts... isn't this the same old college behavior, cramming before the test, waiting till the deadline before a superhuman effort is required to get the thing done, so I can get the adrenalin rush of an amazing achievement?
But then part of me answers back -- maybe there's some value to this kind of procrastination -- letting things stew till their properly cooked. :-)
Reply by Christine B
I know what you mean about worrying that it's a repeat of "usual" last minute behaviour but I've found that it feels completely different. The stress isn't there, the panic isn't there and I am not frantically trying to cram everything in at the last minute. it may be done at the last minute but it has been on the basis of working productively on an hour's work in an hour rather than feeling I've tried to cram 6 hours work into that hour and not done a particularly good job at it.
Reply by Mark Forster
Christine and Seraphim:
I had a very good example of this a week or so ago. I had to circulate the members of a new committee to find the best day to have the next meeting. It was more complicated than it sounds because some members were still being recruited, and not all were on email.
Anyway I started panicking because some of the related action didn't stand out for me on AF. So what I then did was change the system so that the action would get done. Result: a huge increase in resistance to the whole project.
Two days later I went back to "pure" AF and the tasks got done without fuss, but probably later than I would have done them if I'd stuck to AF.
I learnt my lesson!
I had a very good example of this a week or so ago. I had to circulate the members of a new committee to find the best day to have the next meeting. It was more complicated than it sounds because some members were still being recruited, and not all were on email.
Anyway I started panicking because some of the related action didn't stand out for me on AF. So what I then did was change the system so that the action would get done. Result: a huge increase in resistance to the whole project.
Two days later I went back to "pure" AF and the tasks got done without fuss, but probably later than I would have done them if I'd stuck to AF.
I learnt my lesson!
Reply by Christine B
So Mark, I guess my premonition was right!
Reply by Mark Forster
Just trust the system and use the common sense rule when necessary. Yep!
Reply by Christine B
Wow - a new benefit - AF gives ability to predict the future :-)
Reply by Mark Forster
Perhaps we're only just beginning to understand what it's really all about!
Reply by Seraphim
Just for fun, I wonder what will happen if I dismiss a mission-critical task with a hard deadline?
So far I haven't been willing to do that, even though the task didn't really "stand out". I worked on them because I HAD to, not because I got that "standing out" feeling.
Hm, wonder if I'd get a written notice from my manager or something? Is it worth the risk? I'd certainly need to justify my lack of action, and I'm not so sure "Autofocus told me to do something else" and "It just didn't stand out" would go over so well... :-)
I'll let you know how it turns out...
So far I haven't been willing to do that, even though the task didn't really "stand out". I worked on them because I HAD to, not because I got that "standing out" feeling.
Hm, wonder if I'd get a written notice from my manager or something? Is it worth the risk? I'd certainly need to justify my lack of action, and I'm not so sure "Autofocus told me to do something else" and "It just didn't stand out" would go over so well... :-)
I'll let you know how it turns out...
Reply by Seraphim
To follow up on my last post a minute ago, the reason it's hard to explain some of this to my manager, is precisely because AF operates at the intuitive level. One doesn't always immediately understand WHY AF is prompting you to do (or not do) something. It's not so easy to articulate those intuitive reasons. Though I think the whole AF process is making it easier...
Reply by Christine B
Hi Seraphim
So far none of my decisions to go with AF have caused me to miss a deadline and although I have had to do some of the work partially outside the system (in that it has been when I have felt the time to be right but have not necessarily been on the right page) the completion of those tasks has been drastically different, with less stress, no sense of panic, and sometimes with a complete change of method.
You seem to me to be articulating the intuitive side pretty well from your various posts. Have you thought about recommending AF to your manager?
So far none of my decisions to go with AF have caused me to miss a deadline and although I have had to do some of the work partially outside the system (in that it has been when I have felt the time to be right but have not necessarily been on the right page) the completion of those tasks has been drastically different, with less stress, no sense of panic, and sometimes with a complete change of method.
You seem to me to be articulating the intuitive side pretty well from your various posts. Have you thought about recommending AF to your manager?
Reply by Mark Forster
Christine:
That's certainly been my experience as well - that AF makes me more likely to meet a deadline rather than less... and with considerably less stress too.
That's certainly been my experience as well - that AF makes me more likely to meet a deadline rather than less... and with considerably less stress too.
Reply by Seraphim
I have the same experience -- AF certainly does help me meet deadlines.
I'm just thinking about pushing the edges of the system, to see how far I can really trust it under difficult circumstances. These are "what if" scenarios at this point...
Maybe those mission-critical tasks with a hard deadline will just always "stand out", and thereby never get missed.
But what happens if I *do* dismiss it? That's what I'm interested in. Will it become clear that the "mission critical" task really wasn't so mission critical? Will I be able to communicate that to my manager? Or will the task just pop back up again on the end of my list because (1) I caught it when reviewing dismissed tasks or (2) it came into my mind that I hadn't done it yet! Or (worst case) will the task just get missed, and cause trouble for me, my manager, and our project?
These are the areas where I am finding I am still reluctant to "trust the system" and still get tempted to "make exceptions". I do lean toward trusting the system, since I've found it to work so well. But I still have reservations about some of these scenarios.
I'm just thinking about pushing the edges of the system, to see how far I can really trust it under difficult circumstances. These are "what if" scenarios at this point...
Maybe those mission-critical tasks with a hard deadline will just always "stand out", and thereby never get missed.
But what happens if I *do* dismiss it? That's what I'm interested in. Will it become clear that the "mission critical" task really wasn't so mission critical? Will I be able to communicate that to my manager? Or will the task just pop back up again on the end of my list because (1) I caught it when reviewing dismissed tasks or (2) it came into my mind that I hadn't done it yet! Or (worst case) will the task just get missed, and cause trouble for me, my manager, and our project?
These are the areas where I am finding I am still reluctant to "trust the system" and still get tempted to "make exceptions". I do lean toward trusting the system, since I've found it to work so well. But I still have reservations about some of these scenarios.
Reply by Christine B
I think we have to make our decisions based on how strongly we feel about the task at hand and how strong our gut instinct is. To a degree that will depend upon the importance of the task and the penalty for not meeting the deadline - if we were due to appear in court then the "I didn't feel it was the right time" reason might not be appreciated and we can be pretty sure about the penalty.
From experience so far, when a task gets to dismissal stage it is clear why it is being dismissed or alternatively what the reason for the resistance is so that the course of action can be chosen in an informed way.
If you are reviewing your lists regularly a crtitical task is unlikely to get missed - if you decide not to action it it will be more likely to be a conscious and informed decision than otherwise. Your subconscious is after all aware of the deadlines involved.
However at the end of the day you can only see what happens when it happens - hypothetical doesn't work well with AF because your subconscious knows it is only hypothetical.
There's a saying that we need to decide which bridges to cross and which to burn - we cannot do either until we reach them.
From experience so far, when a task gets to dismissal stage it is clear why it is being dismissed or alternatively what the reason for the resistance is so that the course of action can be chosen in an informed way.
If you are reviewing your lists regularly a crtitical task is unlikely to get missed - if you decide not to action it it will be more likely to be a conscious and informed decision than otherwise. Your subconscious is after all aware of the deadlines involved.
However at the end of the day you can only see what happens when it happens - hypothetical doesn't work well with AF because your subconscious knows it is only hypothetical.
There's a saying that we need to decide which bridges to cross and which to burn - we cannot do either until we reach them.
Reply by Catherine CS
I don't think you could ever dismiss a mission critical item (other than rephrasing it to make it more "doable" or transferring it to your calendar) because then if you could dismiss it, it wouldn't be mission critical. It may be the last thing on your list and it may not stand out in the way that items stand out when a page is new but some things are always going to be horrible to start. Why AF is so powerful is that it creates another option which is worse - dismissing the task which effectively adds another task to the page in addition to the one you are resisting and you can do either but you have to do one. If the task is important that in comparison that horrible task doesn't seem so horrible (much less horrible than dismissing it when it's mission critical).
If you started finding yourself dismissing items that were truly mission critical then that would be a signal that you were not committed to the project and if the project was a fundamental part of your job, that you were not committed to your job. Could be your subconscious saying that you need a job change?
If you started finding yourself dismissing items that were truly mission critical then that would be a signal that you were not committed to the project and if the project was a fundamental part of your job, that you were not committed to your job. Could be your subconscious saying that you need a job change?
Reply by Mark Forster
Seraphim (and others):
I know we talk about "trusting the system", which makes it sound as if it's some sort of external power, but I think it's important to remember that it's actually us who are in charge. AF simply gives us a framework to think more effectively. It's not an excuse for behaving irresponsibly in any way.
I know we talk about "trusting the system", which makes it sound as if it's some sort of external power, but I think it's important to remember that it's actually us who are in charge. AF simply gives us a framework to think more effectively. It's not an excuse for behaving irresponsibly in any way.